Add intermediary spacing values #8038
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Hey thanks for the suggestion! Going to say no to this for now as I really don't want the default spacing values to get so close together throughout the scale that it starts to feel like there's no really any constraints. I would suggest just adding these values to your config or using arbitrary values like |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi :),
I am submitting a PR to add a bit more intermediary values on the lower end. I would understand if you would prefer to not merge this but let me explain the use case.
We plan to use Tailwind in the context of themes (so we are reselling a project with the code for developers to extend it). This means that some people may not be familiar with Tailwind at all. As a consequence, we would like to ship a config file that is as much as possible "barebones", to ease the curve so that developers who want to extend our themes can do so without having to also learn 1000 lines of config. The config cannot be avoided in some cases of course, but we feel that for spacing, we want to limit them as much as possible as it creates noise in the file.
With JIT it does not feel like a big problem, and values like 18px (and some intermediary values) on the lower end are often wanted by designers.